Rust Typed Builder
Creates a compile-time verified builder:
extern crate typed_builder;
Build in any order:
.x.y.z.build;
builder.z.x.y.build;
builder
Omit optional fields(the one marked with #[default]
):
.x.build
builder
But you can't omit non-optional arguments - or it won't compile:
.build; // missing x
builder.x.y.y; // y is specified twice
builder
Features
- Custom derive for generating the builder pattern.
- All setters are accepting
Into
values. - Compile time verification that all fields are set before calling
.build()
. - Compile time verification that no field is set more than once.
- Ability to annotate fields with
#[builder(default)]
to make them optional and specify a default value when the user does not set them. - Generates simple documentation for the
.builder()
method.
Limitations
- The build errors when you neglect to set a field or set a field describe the actual problem as a deprecation warning, not as the main error.
- The generated builder type has ugly internal name and many generic parameters. It is not meant for passing around and doing fancy builder tricks - only for nicer object creation syntax(constructor with named arguments and optional arguments).
- For the that reason, all builder methods are call-by-move and the builder is not cloneable. Saves the trouble of determining if the fields are cloneable...
- If you want a builder you can pass around, check out derive-builder. It's API does not conflict with typed-builder's so you can be able to implement them both on the same type.
Alternatives - and why typed-builder is better
- derive-builder - does all the checks in runtime, returning a
Result
you need to unwrap. - safe-builder-derive - this one does compile-time checks - by generating a type for each possible state of the builder. Rust can remove the dead code, but your build time will still be exponential. typed-builder is encoding the builder's state in the generics arguments - so Rust will only generate the path you actually use.
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.